You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Valentin Valchev (JIRA)" <ji...@apache.org> on 2010/03/10 11:31:27 UTC
[jira] Updated: (FELIX-2185) easy plugin prototyping - tools for
developers
[ https://issues.apache.org/jira/browse/FELIX-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Valentin Valchev updated FELIX-2185:
------------------------------------
Attachment: build.xml
> easy plugin prototyping - tools for developers
> ----------------------------------------------
>
> Key: FELIX-2185
> URL: https://issues.apache.org/jira/browse/FELIX-2185
> Project: Felix
> Issue Type: New Feature
> Components: Web Console
> Reporter: Valentin Valchev
> Attachments: build.xml
>
>
> With the current web console, after being updated to JQuery + JQuery UI the plugin structure becomes quite clear and simple:
> 1. There is a Servlet (AbstractWebConsolePlugin), which main role is to generate the required data for the plugin, typically a JSON and execute actions.
> 2. Although the actual rendering is in the Servlet, it use a template file, that contains the HTML markup
> 3. The main logic, that makes the interface interactive is JavaScript code, that uses the JSON from the Servlet and modifies the HTML markup.
> This separation makes it quite easy to develop applications in a static way replacing the upper components with:
> 1. a sample JSON data, statically generated
> 2. a HTML file that is equals to : header + template + footer
> 3. almost the same JavaScript code, that instead of using AJAX request to obtain the data, uses the sample data in 1.
> I must say, that personally have developer several plugins exactly using static HTML file.
> Although easy it consumes time to create that empty HTML file and start developing the plugin. It would be much easier, if we have an option to automatically generate a zip file - containing the HTML updated with the latest header footer, the JavaScript libraries, included by default (e.g. res/lib/) folder, common images and webconsole.css file.
> This task can be easily achieved with modern build tools. Because my minimal knowledge of the Maven build system, I've implemented that task in a simple ANT build file, which must be placed in the webconsole root folder. When ant is invoked with that file, it will generate a file named 'static-test.zip' that contains a template, which is ready for modification and includes up-to-date sources.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (FELIX-2185) easy plugin prototyping - tools
for developers
Posted by Felix Meschberger <fm...@gmail.com>.
Hi,
On 17.03.2010 09:02, Guillaume Nodet wrote:
> What about a maven archetype ?
This would definitely be a big win.
But this is another issue. The thing here is IIUIC to create a simple
tool to mock plugin displays. Of course we could create such a thing
with maven, too.
Regards
Felix
>
> On Wed, Mar 17, 2010 at 08:39, Valentin Valchev <v_...@prosyst.bg> wrote:
>> On 17.3.2010 г. 08:58, Felix Meschberger wrote:
>>> Hi,
>>>
>>> On 17.03.2010 07:50, Valentin Valchev wrote:
>>>
>>>> On 17.3.2010 г. 08:39, Felix Meschberger wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> This sounds like we could just create a page on the site below the Web
>>>>> Console extension page which contains some recipie for prototyping and
>>>>> attaching the build.xml file.
>>>>>
>>>>>
>>>> And already pre-build zip file containing the static code maybe;)
>>>>
>>> Yes ;-)
>>>
>>>
>>>> Unfortunately that zip file should be updated every time we update the
>>>> main page template, or JS & CSS libraries.
>>>>
>>> Could the ant file not GET the files from SVN at build time ?
>>>
>> ANT cannot download recursively a folder but only files and our theme
>> folder contains a lot of them. But maybe it is possible to download the
>> zip archive from JQuery UI web site. And if file-by-file is specified,
>> the build.xml should be updated every time, we add a new javascript
>> library in res/lib folder.
>>
>>
>>> Regards
>>> Felix
>>>
>>
>>
>> --
>>
>> -------------------------------------------------
>> Valentin Valchev · Lead Software Engineer
>> ProSyst Labs EOOD
>> 1606 Sofia, Bulgaria · 48 Vladajska Str.
>> Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17
>> http://www.prosyst.com · v.valchev@prosyst.bg
>> -------------------------------------------------
>> stay in touch with your product.
>> -------------------------------------------------
>>
>>
>
>
>
Re: [jira] Updated: (FELIX-2185) easy plugin prototyping - tools for
developers
Posted by Guillaume Nodet <gn...@gmail.com>.
What about a maven archetype ?
On Wed, Mar 17, 2010 at 08:39, Valentin Valchev <v_...@prosyst.bg> wrote:
> On 17.3.2010 г. 08:58, Felix Meschberger wrote:
>> Hi,
>>
>> On 17.03.2010 07:50, Valentin Valchev wrote:
>>
>>> On 17.3.2010 г. 08:39, Felix Meschberger wrote:
>>>
>>>> Hi,
>>>>
>>>> This sounds like we could just create a page on the site below the Web
>>>> Console extension page which contains some recipie for prototyping and
>>>> attaching the build.xml file.
>>>>
>>>>
>>> And already pre-build zip file containing the static code maybe;)
>>>
>> Yes ;-)
>>
>>
>>> Unfortunately that zip file should be updated every time we update the
>>> main page template, or JS & CSS libraries.
>>>
>> Could the ant file not GET the files from SVN at build time ?
>>
> ANT cannot download recursively a folder but only files and our theme
> folder contains a lot of them. But maybe it is possible to download the
> zip archive from JQuery UI web site. And if file-by-file is specified,
> the build.xml should be updated every time, we add a new javascript
> library in res/lib folder.
>
>
>> Regards
>> Felix
>>
>
>
> --
>
> -------------------------------------------------
> Valentin Valchev · Lead Software Engineer
> ProSyst Labs EOOD
> 1606 Sofia, Bulgaria · 48 Vladajska Str.
> Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17
> http://www.prosyst.com · v.valchev@prosyst.bg
> -------------------------------------------------
> stay in touch with your product.
> -------------------------------------------------
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: [jira] Updated: (FELIX-2185) easy plugin prototyping - tools
for developers
Posted by Valentin Valchev <v_...@prosyst.bg>.
On 17.3.2010 г. 08:58, Felix Meschberger wrote:
> Hi,
>
> On 17.03.2010 07:50, Valentin Valchev wrote:
>
>> On 17.3.2010 г. 08:39, Felix Meschberger wrote:
>>
>>> Hi,
>>>
>>> This sounds like we could just create a page on the site below the Web
>>> Console extension page which contains some recipie for prototyping and
>>> attaching the build.xml file.
>>>
>>>
>> And already pre-build zip file containing the static code maybe;)
>>
> Yes ;-)
>
>
>> Unfortunately that zip file should be updated every time we update the
>> main page template, or JS & CSS libraries.
>>
> Could the ant file not GET the files from SVN at build time ?
>
ANT cannot download recursively a folder but only files and our theme
folder contains a lot of them. But maybe it is possible to download the
zip archive from JQuery UI web site. And if file-by-file is specified,
the build.xml should be updated every time, we add a new javascript
library in res/lib folder.
> Regards
> Felix
>
--
-------------------------------------------------
Valentin Valchev · Lead Software Engineer
ProSyst Labs EOOD
1606 Sofia, Bulgaria · 48 Vladajska Str.
Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17
http://www.prosyst.com · v.valchev@prosyst.bg
-------------------------------------------------
stay in touch with your product.
-------------------------------------------------
Re: [jira] Updated: (FELIX-2185) easy plugin prototyping - tools
for developers
Posted by Felix Meschberger <fm...@gmail.com>.
Hi,
On 17.03.2010 07:50, Valentin Valchev wrote:
> On 17.3.2010 г. 08:39, Felix Meschberger wrote:
>> Hi,
>>
>> This sounds like we could just create a page on the site below the Web
>> Console extension page which contains some recipie for prototyping and
>> attaching the build.xml file.
>>
> And already pre-build zip file containing the static code maybe;)
Yes ;-)
> Unfortunately that zip file should be updated every time we update the
> main page template, or JS & CSS libraries.
Could the ant file not GET the files from SVN at build time ?
Regards
Felix
>
>> WDYT ?
>>
>> Regards
>> Felix
>>
>> On 10.03.2010 11:31, Valentin Valchev (JIRA) wrote:
>>
>>> [ https://issues.apache.org/jira/browse/FELIX-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>
>>> Valentin Valchev updated FELIX-2185:
>>> ------------------------------------
>>>
>>> Attachment: build.xml
>>>
>>>
>>>> easy plugin prototyping - tools for developers
>>>> ----------------------------------------------
>>>>
>>>> Key: FELIX-2185
>>>> URL: https://issues.apache.org/jira/browse/FELIX-2185
>>>> Project: Felix
>>>> Issue Type: New Feature
>>>> Components: Web Console
>>>> Reporter: Valentin Valchev
>>>> Attachments: build.xml
>>>>
>>>>
>>>> With the current web console, after being updated to JQuery + JQuery UI the plugin structure becomes quite clear and simple:
>>>> 1. There is a Servlet (AbstractWebConsolePlugin), which main role is to generate the required data for the plugin, typically a JSON and execute actions.
>>>> 2. Although the actual rendering is in the Servlet, it use a template file, that contains the HTML markup
>>>> 3. The main logic, that makes the interface interactive is JavaScript code, that uses the JSON from the Servlet and modifies the HTML markup.
>>>> This separation makes it quite easy to develop applications in a static way replacing the upper components with:
>>>> 1. a sample JSON data, statically generated
>>>> 2. a HTML file that is equals to : header + template + footer
>>>> 3. almost the same JavaScript code, that instead of using AJAX request to obtain the data, uses the sample data in 1.
>>>> I must say, that personally have developer several plugins exactly using static HTML file.
>>>> Although easy it consumes time to create that empty HTML file and start developing the plugin. It would be much easier, if we have an option to automatically generate a zip file - containing the HTML updated with the latest header footer, the JavaScript libraries, included by default (e.g. res/lib/) folder, common images and webconsole.css file.
>>>> This task can be easily achieved with modern build tools. Because my minimal knowledge of the Maven build system, I've implemented that task in a simple ANT build file, which must be placed in the webconsole root folder. When ant is invoked with that file, it will generate a file named 'static-test.zip' that contains a template, which is ready for modification and includes up-to-date sources.
>>>>
>>>
>>
>>
>
>
Re: [jira] Updated: (FELIX-2185) easy plugin prototyping - tools
for developers
Posted by Valentin Valchev <v_...@prosyst.bg>.
On 17.3.2010 г. 08:39, Felix Meschberger wrote:
> Hi,
>
> This sounds like we could just create a page on the site below the Web
> Console extension page which contains some recipie for prototyping and
> attaching the build.xml file.
>
And already pre-build zip file containing the static code maybe;)
Unfortunately that zip file should be updated every time we update the
main page template, or JS & CSS libraries.
> WDYT ?
>
> Regards
> Felix
>
> On 10.03.2010 11:31, Valentin Valchev (JIRA) wrote:
>
>> [ https://issues.apache.org/jira/browse/FELIX-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>
>> Valentin Valchev updated FELIX-2185:
>> ------------------------------------
>>
>> Attachment: build.xml
>>
>>
>>> easy plugin prototyping - tools for developers
>>> ----------------------------------------------
>>>
>>> Key: FELIX-2185
>>> URL: https://issues.apache.org/jira/browse/FELIX-2185
>>> Project: Felix
>>> Issue Type: New Feature
>>> Components: Web Console
>>> Reporter: Valentin Valchev
>>> Attachments: build.xml
>>>
>>>
>>> With the current web console, after being updated to JQuery + JQuery UI the plugin structure becomes quite clear and simple:
>>> 1. There is a Servlet (AbstractWebConsolePlugin), which main role is to generate the required data for the plugin, typically a JSON and execute actions.
>>> 2. Although the actual rendering is in the Servlet, it use a template file, that contains the HTML markup
>>> 3. The main logic, that makes the interface interactive is JavaScript code, that uses the JSON from the Servlet and modifies the HTML markup.
>>> This separation makes it quite easy to develop applications in a static way replacing the upper components with:
>>> 1. a sample JSON data, statically generated
>>> 2. a HTML file that is equals to : header + template + footer
>>> 3. almost the same JavaScript code, that instead of using AJAX request to obtain the data, uses the sample data in 1.
>>> I must say, that personally have developer several plugins exactly using static HTML file.
>>> Although easy it consumes time to create that empty HTML file and start developing the plugin. It would be much easier, if we have an option to automatically generate a zip file - containing the HTML updated with the latest header footer, the JavaScript libraries, included by default (e.g. res/lib/) folder, common images and webconsole.css file.
>>> This task can be easily achieved with modern build tools. Because my minimal knowledge of the Maven build system, I've implemented that task in a simple ANT build file, which must be placed in the webconsole root folder. When ant is invoked with that file, it will generate a file named 'static-test.zip' that contains a template, which is ready for modification and includes up-to-date sources.
>>>
>>
>
>
--
-------------------------------------------------
Valentin Valchev · Lead Software Engineer
ProSyst Labs EOOD
1606 Sofia, Bulgaria · 48 Vladajska Str.
Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17
http://www.prosyst.com · v.valchev@prosyst.bg
-------------------------------------------------
stay in touch with your product.
-------------------------------------------------
Re: [jira] Updated: (FELIX-2185) easy plugin prototyping - tools
for developers
Posted by Felix Meschberger <fm...@gmail.com>.
Hi,
This sounds like we could just create a page on the site below the Web
Console extension page which contains some recipie for prototyping and
attaching the build.xml file.
WDYT ?
Regards
Felix
On 10.03.2010 11:31, Valentin Valchev (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/FELIX-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Valentin Valchev updated FELIX-2185:
> ------------------------------------
>
> Attachment: build.xml
>
>> easy plugin prototyping - tools for developers
>> ----------------------------------------------
>>
>> Key: FELIX-2185
>> URL: https://issues.apache.org/jira/browse/FELIX-2185
>> Project: Felix
>> Issue Type: New Feature
>> Components: Web Console
>> Reporter: Valentin Valchev
>> Attachments: build.xml
>>
>>
>> With the current web console, after being updated to JQuery + JQuery UI the plugin structure becomes quite clear and simple:
>> 1. There is a Servlet (AbstractWebConsolePlugin), which main role is to generate the required data for the plugin, typically a JSON and execute actions.
>> 2. Although the actual rendering is in the Servlet, it use a template file, that contains the HTML markup
>> 3. The main logic, that makes the interface interactive is JavaScript code, that uses the JSON from the Servlet and modifies the HTML markup.
>> This separation makes it quite easy to develop applications in a static way replacing the upper components with:
>> 1. a sample JSON data, statically generated
>> 2. a HTML file that is equals to : header + template + footer
>> 3. almost the same JavaScript code, that instead of using AJAX request to obtain the data, uses the sample data in 1.
>> I must say, that personally have developer several plugins exactly using static HTML file.
>> Although easy it consumes time to create that empty HTML file and start developing the plugin. It would be much easier, if we have an option to automatically generate a zip file - containing the HTML updated with the latest header footer, the JavaScript libraries, included by default (e.g. res/lib/) folder, common images and webconsole.css file.
>> This task can be easily achieved with modern build tools. Because my minimal knowledge of the Maven build system, I've implemented that task in a simple ANT build file, which must be placed in the webconsole root folder. When ant is invoked with that file, it will generate a file named 'static-test.zip' that contains a template, which is ready for modification and includes up-to-date sources.
>