nacho carmenynacho.com schrieb:
> Hola Jorge:
>
>> You should also take a look at the form definition
in
>> intake.xml A line-by-line debugging of the code at
>> doSubmitfile will probably enlight you...
>>
>
> That bit about intake.xml did the trick ;), i was lost
with the intake
> thing, reviewed the intake docs and now i get it..
>
> We have modified Wizard3.vm and ReportIssue.java to
have 3 Attach boxes, in
> a very rought way thought, but it works.. we'll try to
make the nummber
> attach boxes configurable, any advice about where to
put this config info in
> a scarab's way will be highly appreciated..
>
> We need too to copy the first description to all the
other attach boxes, how
> can i do it ? I was thinking of make the other data
field hidden and copy
> the first data field to all the other with
> js trick.. How it sounds?
>
> Many thanks, i will contribute a patch if anybody is
interested..
>
hy, Ignacio
first of all congrats for finding your solution! I usually
get
quite some embarrassing hours whenever i need to touch the
intake stuff.
indeed i never reached complete understanding here. Maybe
one of your
best contribs could be a howto intake entry in the scarab
wiki or
at least some pointers of where to find good! tutorials...
ok, for the contribution part i have some severe doubts.
IMHO the main problem is how we can obtain a clean interface
which
allows us to configure our frontend in various ways, rather
than hacking
it in uncontrollable ways. Not that i want to say, your
contrib is a hack,
but its OTOH not so mainstream that it is a must in the GUI.
You can find
several places around Scarab user interface where we
constantly live with
rather croude constraints since many years. i dont like the
idea to add
new ones...
Maybe we should think about an approach which allows more
flexibility but
also restricts the interface to basic but usefull
functionality?
e.g:
instead of thinking about how to solve the problem with
putting the same
description into all description fields for your
attachements, it might be
better to think about how we could create a basic attachment
api, where we
can abstract to something more elegant, more straight
forward and as such
better to understand/use.
i.e. in your particular case it sounds meanigfull to have a
relation between
all your attachments, such that all attachments build a
single group with a single
description field. That at itself sounds good and
meaningfull. I wanted this
features once in a while too. But imho this can not be
limited to single shot,
such that when i want to organize several attachments into
separate groups i
must not be forced to upload them all at once.
OTOH it is a good idea to support bulk uploads, because it
usually bulkupload
is very handy. So probably we would want bulk upload AND
(possibly even hiearchical)
organization of attachments per issue ...
It should not be too complex to enhance the interface here
and do some uplifting
in the attachments area. So as from me you are welcome to
contrib here. Maybe it
is best to start another Enhancements issue for this ?
So WDYT ?
thanks, hussayn
> Saludos,
> Ignacio J. Ortega
>
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribe scarab.tigris.org
> For additional commands, e-mail: dev-help scarab.tigris.org
>
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
tel.: +49 221 560 11 0
fax.: +49 221 560 11 20
mailto:info saxess.de
http://www.saxess.de
http://www.saxess.com
http://www.saxess.org
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe scarab.tigris.org
For additional commands, e-mail: dev-help scarab.tigris.org
|