<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Position?]]></title><description><![CDATA[<p dir="auto">On FOP 1 there is the Position= entry in the config, so I could customize per department sections on the flash panel.  I don't really see a way to do this on FOP2.</p>
<p dir="auto">Other than that, this looks great!</p>
<p dir="auto">Also, is the demo just restricted to 15 buttons total, so if it grabbed more than 15 extensions, it won't show any queues?</p>
<p dir="auto">Jason</p>
]]></description><link>http://localhost:4567/topic/7/position</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 06:41:01 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/7.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 29 Jun 2009 13:12:53 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Position? on Mon, 03 Aug 2009 13:44:13 GMT]]></title><description><![CDATA[<p dir="auto">Hi hbondy,</p>
<p dir="auto">Ok.. I have just added that feature on the devel branch. Specify "group=something" to the button definition and it will create a "something" section in the display just below the regular extension list. I will try now to continue working on trunk details (I will leave actions on trunk lines for a future release as it will take quite some time to do). And finally I will also try to tackle parking, but I believe it will have to wait a little longer as it is not that simple..</p>
<p dir="auto">Regards,</p>
]]></description><link>http://localhost:4567/post/43</link><guid isPermaLink="true">http://localhost:4567/post/43</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Mon, 03 Aug 2009 13:44:13 GMT</pubDate></item><item><title><![CDATA[Reply to Position? on Sun, 02 Aug 2009 22:35:31 GMT]]></title><description><![CDATA[<p dir="auto">Well,  there sort of is a need to somehow separate the sections in a multi-user/multi-tenant setup (similar to departments).  It would be nice to group all of the tenant A extensions together.  Now, I know that I can simply just keep them in order in the button.cfg file, but the ability to put in subheadings like Extensions - Tenant 1, then Extensions - Tenant 2, etc... would be nice.</p>
<p dir="auto">Otherwise the product is great.</p>
]]></description><link>http://localhost:4567/post/42</link><guid isPermaLink="true">http://localhost:4567/post/42</guid><dc:creator><![CDATA[hbondy]]></dc:creator><pubDate>Sun, 02 Aug 2009 22:35:31 GMT</pubDate></item><item><title><![CDATA[Reply to Position? on Mon, 29 Jun 2009 13:26:22 GMT]]></title><description><![CDATA[<p dir="auto">There is no need for positions in fop2. If you have 500 buttons you will scroll down. The order is the appearance on the button config file.</p>
<p dir="auto">The demo is restricted to 15 buttons, you will be able to see the first 15 buttons defined in your button config file. As I said, the order is the one of appearance, if you have the queue button defined at the very top, it will work.</p>
<p dir="auto">Best regards,</p>
]]></description><link>http://localhost:4567/post/41</link><guid isPermaLink="true">http://localhost:4567/post/41</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Mon, 29 Jun 2009 13:26:22 GMT</pubDate></item></channel></rss>