irmis-devel Mailing List for IRMIS
Status: Alpha
Brought to you by:
carcassi
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(2) |
Feb
(10) |
Mar
(5) |
Apr
(5) |
May
(1) |
Jun
(3) |
Jul
(3) |
Aug
(1) |
Sep
(2) |
Oct
(2) |
Nov
(1) |
Dec
(1) |
| 2010 |
Jan
(2) |
Feb
(1) |
Mar
(1) |
Apr
(3) |
May
(2) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(1) |
| 2011 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
1
|
2
|
3
|
4
|
5
|
6
|
|
7
|
8
|
9
|
10
|
11
|
12
(2) |
13
|
|
14
|
15
|
16
|
17
|
18
|
19
|
20
|
|
21
|
22
|
23
|
24
|
25
|
26
(1) |
27
|
|
28
|
29
|
30
|
|
|
|
|
|
From: Carcassi, G. <car...@bn...> - 2009-06-26 17:44:32
|
Hi all, It's that time of the month: https://sourceforge.net/project/showfiles.php?group_id=226514&package_id =274120 Most of my attention has been directed on finishing up the new ComponentEditor, and I believe it is in a good enough shape to replace the old one. Part of that effort also included redesigning some of the basic building blocks of the GUIs, which will affect the other applications as well. For example: component trees now support arbitrary ordering (for example, by logical description, by component type, etc...); the short trees to display the ancestry better support multiple parents and partially parented components. We also have contributions from Doug Sheffer, an MSU student who is spending the summer here at BNL. He added a server side safety check to make sure circular references are not added to the component hierarchy. He relaxed the constraints on componentType update, allowing to add/remove Interfaces and Ports on already defined ComponentType. And he has added support do describe Channels in ComponentTypes. Full change log is available on Trac at: http://apps.sourceforge.net/trac/irmis/query?status=closed&group=compone nt&order=priority&col=id&col=summary&col=owner&col=type&col=priority&col =component&col=version&milestone=3.0.8-alpha%20(r924) <http://apps.sourceforge.net/trac/irmis/query?status=closed&group=compon ent&order=priority&col=id&col=summary&col=owner&col=type&col=priority&co l=component&col=version&milestone=3.0.8-alpha%20(r924)> Next month we will continue cleaning up of the GUIs and add channel support in them. Gabriele |
|
From: Carcassi, G. <car...@bn...> - 2009-06-12 20:58:44
|
Hi all, We just had a planning exercise here at BNL, and I wanted to share the result. I have a list of our projected deadlines for the rest of this calendar year, which more or less says what I'll be concentrating my work on these next 6 months. I also have a list of should have's, meaning what I would work on if I finish the other tasks earlier. Then there is the rest of the laundry list, not prioritized in any particular order. Naturally the nature of any plans is to be revised later, so take it with a grain of salt... June: Cable pull support (in terms of API and scripting, no GUI) July: Channel Support Files and Fieldmaps September: Split component table to prepare for future configuration support Save/restore October: PV introspection Should have (prioritized): Security support Configuration support Past 2009 (not prioritized): Cable pull support in Cable editor Component history Prescriptive PV Rest of Descriptive PV EPICS device support Alignment IOC support When I have a chance, I'll put this information in Trac. Gabriele |
|
From: Carcassi, G. <car...@bn...> - 2009-06-12 20:51:11
|
Hi Rami, Sorry for the late reply but it has been a busy week. Also, please post to the irmis-devel list as irmis-svn should not really be the list for discussions. Unfortunately I don't have a definitive answer for when we'll have authN/authZ: it is something that we would want to have before the end of the calendar year, we would prefer having it earlier, but it is not tied to any specific deadline we have to meet at BNL: it is not critical _at this moment_ for us and other functionality is (I am going to send another e-mail on planning in a moment). More precise than that would be giving you a date that can at any point be pushed back because something else pops up the stack. The good news that the design is already done: it's just a matter of taking the time to implement it. I am not aware of anybody who uses IRMIS+glassfish+security. My suggestion is the same as before: either think about a temporary solution at your site, or think about contributing the solution... Thanks, Gabriele From: Rami Ahmad [mailto:ram...@gm...] Sent: Saturday, June 06, 2009 9:12 AM To: Carcassi, Gabriele Cc: Irm...@li... Subject: Re: [Irmis-svn] authentication in IRMIS Hi Gabriele, When do you expect to have the authentication on IRMIS done? yeah I know there are many way to secure the application but I prefer to have it built in in the application. does anyone secure IRMIS using glassfish?? if yes please send the instructions.. Regards Rami |