Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: pass (athena.apache.org: domain of fmeschbe@gmail.com designates
 209.85.220.218 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=S/whz0dnaznd8hCXR2QISVNVQZLmZjis2aHk8LzoVEljeBwzDNZn8DHL22gLHVP2GN
         vpMU8lAfW3OvENkDeWRgc5y1q5KPhwBDFbLUD4g/Ss5pAzI4dGqfKJVzTHxRCwvOWkh+
         esQLuCHxU6orrGUoxXgwLe5wftbXpgTMt2KZc=
Message-ID: <4BA07D9A.7030301@gmail.com>
Date: Wed, 17 Mar 2010 07:58:34 +0100
From: Felix Meschberger <fmeschbe@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.1.8pre) Gecko/20100120 Shredder/3.0.2pre
MIME-Version: 1.0
To: dev@felix.apache.org
Subject: Re: [jira] Updated: (FELIX-2185) easy plugin prototyping - tools
 for developers
References: <2046015000.174641268217087363.JavaMail.jira@brutus.apache.org>
 <4BA0792A.30203@gmail.com> <4BA07BA8.1060502@prosyst.bg>
In-Reply-To: <4BA07BA8.1060502@prosyst.bg>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

On 17.03.2010 07:50, Valentin Valchev wrote:
> On 17.3.2010 =D0=B3. 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.
>>  =20
> 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

>=20
>> WDYT ?
>>
>> Regards
>> Felix
>>
>> On 10.03.2010 11:31, Valentin Valchev (JIRA) wrote:
>>  =20
>>>      [ https://issues.apache.org/jira/browse/FELIX-2185?page=3Dcom.at=
lassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>
>>> Valentin Valchev updated FELIX-2185:
>>> ------------------------------------
>>>
>>>     Attachment: build.xml
>>>
>>>    =20
>>>> easy plugin prototyping - tools for developers
>>>> ----------------------------------------------
>>>>
>>>>                 Key: FELIX-2185
>>>>                 URL: https://issues.apache.org/jira/browse/FELIX-218=
5
>>>>             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 execu=
te actions.
>>>> 2. Although the actual rendering is in the Servlet, it use a templat=
e file, that contains the HTML markup
>>>> 3. The main logic, that makes the interface interactive is JavaScrip=
t code, that uses the JSON from the Servlet and modifies the HTML markup.=

>>>> This separation makes it quite easy to develop applications in a sta=
tic 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 reque=
st to obtain the data, uses the sample data in 1.
>>>> I must say, that personally have developer several plugins exactly u=
sing static HTML file.=20
>>>> Although easy it consumes time to create that empty HTML file and st=
art developing the plugin. It would be much easier, if we have an option =
to automatically generate a zip file - containing the HTML updated with t=
he latest header footer, the JavaScript libraries, included by default (e=
=2Eg. 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 f=
older. When ant is invoked with that file, it will generate a file named =
'static-test.zip' that contains a template, which is ready for modificati=
on and includes up-to-date sources.
>>>>      =20
>>>    =20
>>
>>  =20
>=20
>=20