Home » Language IDEs » ServerTools (WTP) » Start with a Site Wizard
| Start with a Site Wizard [message #12198] |
Mon, 15 December 2003 01:24  |
Eclipse User |
|
|
|
Rather than editor and deployment tools, I suggest this project starts with
a site creation tool where the site developer visually creates a tree
representing a site structure where each node is a page on the browser.
Then each Node will be represented by a parametrized template such that a
developer should be able to logically group these nodes and make them
members of logical groups. For example group A, group B, group C pages. Then
the developer should be able to write parametrized java code or html or do
visual design on a group basis (write code that applies to all pages in
group A, in a paratmetric way, which means when final jsp is generated, the
code for page 1 is not the same as page 2 even though they are both in group
A and code was specified only once but it effected n number of pages in
group A).
For example, developer should be able to visually say group A pages display
child pages on their left side. Then this Eclipse tool should store that
info for the Node and when compiled, it should generate correct html/jsp
code to display child pages, whatever they might be, on the left. Or
developer should be able to write code that says "display parent page name
here" and tell our tool to apply this code to all group B pages and the
exact name of the parent page would depend on the location of the node in
the website hierarchy.
This site structure tool should be designed such that it should be possible
to write jsp code for individual nodes (pages) such that if pages are moved
around, code need not be touched, or can be automatically updated by the
site wizard.
We should also provide visual representation of files included into other
files etc. Developer should also be able to include a file on the exact
relative location of all pages in a given page group. Again the included
file should be able to contain paratmetrized code such that it's contents
can mean one thing for page 1 and another for page 2 and something else for
page 3, yet the content should always be valid. In other words, developer
should be able to say, "Here is some code in file X that displays a banner
with the page title on it. I want this file to be included to all pages of
group A such that it displays the banner with the correct page title of the
page it was included into."
Taking this parametric approach visual design and coding efforts for
individual pages can be minimized.
Anyway, if you have any questions, drop me a line.
Suavi Demir
demir4@yahoo.com
|
|
|
| Re: Start with a Site Wizard [message #16124 is a reply to message #12198] |
Thu, 29 January 2004 08:35  |
| Eclipse User |
|
|
|
Oh no please, not another spaghetti templating framework with XML files full
of ever growing tags to learn. Lomboz does enough for me - a few wizards
(although I could live without them), a plain code editor and an easy
deployment method to many servers. The last thing I want is yet another
bunch of files to configure.
Troll.
"Suavi" <demir4@yahoo.com> wrote in message news:brjk31$ifj$1@eclipse.org...
> Rather than editor and deployment tools, I suggest this project starts
with
> a site creation tool where the site developer visually creates a tree
> representing a site structure where each node is a page on the browser.
>
> Then each Node will be represented by a parametrized template such that a
> developer should be able to logically group these nodes and make them
> members of logical groups. For example group A, group B, group C pages.
Then
> the developer should be able to write parametrized java code or html or do
> visual design on a group basis (write code that applies to all pages in
> group A, in a paratmetric way, which means when final jsp is generated,
the
> code for page 1 is not the same as page 2 even though they are both in
group
> A and code was specified only once but it effected n number of pages in
> group A).
>
> For example, developer should be able to visually say group A pages
display
> child pages on their left side. Then this Eclipse tool should store that
> info for the Node and when compiled, it should generate correct html/jsp
> code to display child pages, whatever they might be, on the left. Or
> developer should be able to write code that says "display parent page name
> here" and tell our tool to apply this code to all group B pages and the
> exact name of the parent page would depend on the location of the node in
> the website hierarchy.
>
> This site structure tool should be designed such that it should be
possible
> to write jsp code for individual nodes (pages) such that if pages are
moved
> around, code need not be touched, or can be automatically updated by the
> site wizard.
>
> We should also provide visual representation of files included into other
> files etc. Developer should also be able to include a file on the exact
> relative location of all pages in a given page group. Again the included
> file should be able to contain paratmetrized code such that it's contents
> can mean one thing for page 1 and another for page 2 and something else
for
> page 3, yet the content should always be valid. In other words, developer
> should be able to say, "Here is some code in file X that displays a banner
> with the page title on it. I want this file to be included to all pages of
> group A such that it displays the banner with the correct page title of
the
> page it was included into."
>
> Taking this parametric approach visual design and coding efforts for
> individual pages can be minimized.
>
> Anyway, if you have any questions, drop me a line.
>
> Suavi Demir
> demir4@yahoo.com
>
>
|
|
|
| Re: Start with a Site Wizard [message #16206 is a reply to message #16124] |
Fri, 30 January 2004 09:38 |
| Eclipse User |
|
|
|
Originally posted by: robert.varga.fathomtechnology.com
I agree.
The tool should not force me to adopt a site structure and a specific
framework
written possibly in someone else's programming style and designed based on
probably entirely
different requirements and design decisions.
I have my own framework. What I want from a tool is to be as flexible in
getting its files from
and putting its stuff to, but not to try to tell me, what I want to do. Also
it should provide me
with the most effective edit methods, syntax highlighting, maybe
hyper-navigation, but it should
not try to think.
Robert Varga
"Troll" <trollfiddler@hotmail.com> wrote in message
news:bvb1ti$dmk$1@eclipse.org...
> Oh no please, not another spaghetti templating framework with XML files
full
> of ever growing tags to learn. Lomboz does enough for me - a few wizards
> (although I could live without them), a plain code editor and an easy
> deployment method to many servers. The last thing I want is yet another
> bunch of files to configure.
>
> Troll.
>
>
> "Suavi" <demir4@yahoo.com> wrote in message
news:brjk31$ifj$1@eclipse.org...
> > Rather than editor and deployment tools, I suggest this project starts
> with
> > a site creation tool where the site developer visually creates a tree
> > representing a site structure where each node is a page on the browser.
> >
> > Then each Node will be represented by a parametrized template such that
a
> > developer should be able to logically group these nodes and make them
> > members of logical groups. For example group A, group B, group C pages.
> Then
> > the developer should be able to write parametrized java code or html or
do
> > visual design on a group basis (write code that applies to all pages in
> > group A, in a paratmetric way, which means when final jsp is generated,
> the
> > code for page 1 is not the same as page 2 even though they are both in
> group
> > A and code was specified only once but it effected n number of pages in
> > group A).
> >
> > For example, developer should be able to visually say group A pages
> display
> > child pages on their left side. Then this Eclipse tool should store that
> > info for the Node and when compiled, it should generate correct html/jsp
> > code to display child pages, whatever they might be, on the left. Or
> > developer should be able to write code that says "display parent page
name
> > here" and tell our tool to apply this code to all group B pages and the
> > exact name of the parent page would depend on the location of the node
in
> > the website hierarchy.
> >
> > This site structure tool should be designed such that it should be
> possible
> > to write jsp code for individual nodes (pages) such that if pages are
> moved
> > around, code need not be touched, or can be automatically updated by the
> > site wizard.
> >
> > We should also provide visual representation of files included into
other
> > files etc. Developer should also be able to include a file on the exact
> > relative location of all pages in a given page group. Again the included
> > file should be able to contain paratmetrized code such that it's
contents
> > can mean one thing for page 1 and another for page 2 and something else
> for
> > page 3, yet the content should always be valid. In other words,
developer
> > should be able to say, "Here is some code in file X that displays a
banner
> > with the page title on it. I want this file to be included to all pages
of
> > group A such that it displays the banner with the correct page title of
> the
> > page it was included into."
> >
> > Taking this parametric approach visual design and coding efforts for
> > individual pages can be minimized.
> >
> > Anyway, if you have any questions, drop me a line.
> >
> > Suavi Demir
> > demir4@yahoo.com
> >
> >
>
>
|
|
|
Goto Forum:
Current Time: Thu May 08 07:11:41 EDT 2025
Powered by FUDForum. Page generated in 0.03318 seconds |
Home